<cmdsynopsis>
<command>ostree remote summary</command> <arg choice="opt" rep="repeat">OPTIONS</arg> <arg choice="req">NAME</arg>
</cmdsynopsis>
+ <cmdsynopsis>
+ <command>ostree remote add-cookie</command>
+ <arg choice="req">NAME</arg>
+ <arg choice="req">DOMAIN</arg>
+ <arg choice="req">PATH</arg>
+ <arg choice="req">COOKIE_NAME</arg>
+ <arg choice="req">VALUE</arg>
+ </cmdsynopsis>
+ <cmdsynopsis>
+ <command>ostree remote delete-cookie</command>
+ <arg choice="req">NAME</arg>
+ <arg choice="req">DOMAIN</arg>
+ <arg choice="req">PATH</arg>
+ <arg choice="req">COOKIE_NAME</arg>
+ <arg choice="req">VALUE</arg>
+ </cmdsynopsis>
+ <cmdsynopsis>
+ <command>ostree remote list-cookies</command> <arg choice="req">NAME</arg>
+ </cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<para>
The GPG keys to import may be in binary OpenPGP format or ASCII armored. The optional <arg>KEY-ID</arg> list can restrict which keys are imported from a keyring file or input stream. All keys are imported if this list is omitted. If neither <option>--keyring</option> nor <option>--stdin</option> options are given, then keys are imported from the user's personal GPG keyring.
</para>
+ <para>
+ The various cookie related command allow management of a remote specific cookie jar.
+ </para>
</refsect1>
<refsect1>
in the section <literal>GPG verification</literal>.
</para>
</refsect1>
+
+ <refsect1>
+ <title>Per-remote HTTP cookies</title>
+ <para>
+ Some content providers may want to control access to remote
+ repositories via HTTP cookies. The <command>ostree remote
+ add-cookie</command> and <command>ostree remote
+ delete-cookie</command> commands will update a per-remote
+ lookaside cookie jar, named
+ <filename>$remotename.cookies.txt</filename>.
+ </para>
+ </refsect1>
<refsect1>
<title>See Also</title>